Post

Replies

Boosts

Views

Activity

How much geometry can you render in memoryless render pass?
I've got an iOS application that renders a lot of geometry. (Lots of objects and in most cases multiple instances of those objects) The app was previously running using OpenGL ES 3.0. I'm just starting in my conversion but already I'm getting the following error:Execution of the command buffer was aborted due to an error during execution. Too much geometry to support memoryless render pass attachments. (IOAF code 13)Is there any way to have some idea of how much geometry is too much? If I continue to get this error, does that mean that I need to switch from a memoryless render pass to two render passes, the first one writing to system memory and the second reading from system memory to perform the lighting?Thanks for any insight anyone can give.
2
0
1k
Nov ’19
Stepping into functions using GPUTrace
I'm trying to debug some shaders that call functions that are in other files. (Specifically I have a ShadowTerm function that is used by many different shaders.) I can bring up the fragment shader in XCode's GPU debugging, but I don't see a way to step into my function ShadowTerm(). Is there a way to step into functions that are in other .metal files?
2
0
807
Dec ’19